What

This merges the soroban-client library (stellar/js-soroban-client) into this package.

The namespaces have changed to move each server-dependent component into its own module. There is a detailed migration guide written here which should outline both the literal (i.e. necessary code changes) and philosophical (i.e. how to find certain functionality) changes needed to adapt to this merge.

The code changes themselves are:

• moving js-soroban-client into src/soroban and its tests into test/unit/server/soroban
• dropping duplicate files (like axios, etc.)
• migrating imports to remove conflicts and make them sensible
• moving namespaces around to separate Horizon and Soroban RPC in a sensible way
• updating tests to work with both libs

Why

It is incredibly likely that most applications will need to interface with both Horizon and Soroban if they plan on supporting the entire feature set that Stellar has to offer. Putting things into a single library means less duplicated dependencies and a better, all-inclusive experience. Additionally, the amount of shared code and build dependencies across these two libraries means it makes sense to combine them into one.

Closes #850.

Known Limitations

• If someone does not care about one server or the other, they may be blowing up their bundle size needlessly.
• It may be better to have a monorepo structure to share build scripts rather than actually combining both libraries.
• User feedback is non-existent, yet essential for determining whether or not this is worthwhile

TODOs Remaining

• Write a migration guide for both Horizon and Soroban RPC users